home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
update20.zip
/
UPDATE.DOC
< prev
next >
Wrap
Text File
|
1989-03-12
|
8KB
|
190 lines
***********************************************************************
* AutoUpdate version 2.00 *
* Copyright 1989, by Steve Jones *
***********************************************************************
This file is part of UPDATE20.ARC, which contains the following
files:
UPDATE.DOC This file
UPDATE.EXE User Update executable file
UPDATE.CTL Sample control file
**DO NOT RUN UPDATE WITH THE DEMO .CFG FILE! IT WILL CHANGE YOUR USERLOG!**
Although as of the release of this program, it is running
reliably on my own system, I can not, and will not be held
responsible for any damages, to your system, due to the use, or
misuse of this program. Much care has been taken to insure the
safety of your BBS's system files (USERS.BBS, and MSG*.BBS), for
example, all message files are closed after each message is sent,
so that a power failure would have a minimal chance of hurting
your data, but, as with any program that modifies these files,
there is always a slight chance that something could go wrong.
Remember: WHEN IN DOUBT, BACK IT UP!
AutoUpdate (formerly UserUpdate) may be distributed freely,
as long as no fee is charged, over the reasonable cost of the
media it is delivered on, or a charge for the connect time
involved with transfering it. The contents of the archive may
not be distributed seperately, but MUST be distributed as some
sort of package, weather it is ARC, PAK, ZIP, or ZOO. If you find
AutoUpdate a valuable tool in running your QuickBBS, please let
me know, by NetMail, at 109/410 in the fidonet, or by writing to:
316 Duxbury Drive
Silver Spring, MD 20904
Flames > nul, please... CONSTRUCTIVE criticism accepted, and
solicited. If you feel it is worth it, include a small donation
with your comments ($5.00 or less...)
The AutoUpdate program's function is to update the QuickBBS
USERS.BBS file, altering ONLY a users access level, depending on
how much they participate on your BBS. It will raise, or lower,
a users access depending on guidelines found in the UPDATE.CTL
file, a sample of which is included with this package.
A new feature of version 2.00 is to also optionally send a message
to the user, alerting him to the fact that his access was changed by
AutoUpdate.
The format of the .CTL file is: A raw ASCII text file, with a
single command and parameter on each line. More than one set of
rules may be in the .CTL file, separated by EXACLY ONE blank
line. The commands are:
Net
Node
Zone
BoardNumber
SecLvlMin
SecLvlMax
SecLvlNew
TimesPosted
HighMsgRead
Times (or TimesCalled, or Called)
Uploads
Downloads
Each command is followed by (at least) one space, and a number.
Net, Node, and Zone, are actually only used in the message sent
to the user. If you don't define these, I am not sure what will
happen, but it *SHOULD* work, as long as the message isn't
placed into your netmail area. On a QuickBBS implementation
without Net/echomail, I suppose these would have no effect.
Boardnumber is the number, 1-200, of the message board that the
messages to the users should be placed into. If this is not
specified, no messages will be sent. Also, you can put a
different board number in each set of update parameters, so that
upgrade notices would be put in one area, and downgrades in
another. You can reset this to 0 if you don't want messages to
be output for a specific set of rules.
The rest of the commands define parameters as to when a user
should be modified. The numbers are the high or low bounds to
qualify the user for that particular change.
Each bound is translated as "If the users value is at least
equal to" the value on the line, then it will be true, unless the
number is preceded by "-", in which case, it will be interpreted
as "if it is not more than" the number. The following is an
example:
SecLvlmin 1
SecLvlMax 10
TimesPosted 3
Times 2
Downloads -2
SecLvlNew 20
This example would effect users with current access of 1 through
10, and update them to 20, if they have posted at least 3
messages, logged on at least twice, and have downloaded LESS THAN
2 files. This example would NOT send messages to the user,
unless a boardnumber was set by a previous set of rules.
(Boardnumber, and node address parameters stay constant until
reset by another command, all others are cleared after each set
of rules)
Case is not important in any of the commands. Also, the commands
may appear in any order. Any commands which are excluded from a
set of rules is ignored when considering that set of rules.
Since any user who doesn't meet even ONE of the parameters will
be ignored, it may be necessary to put in more than one set of
rules (In the above example, you may get a user, who on his first
call, downloads 2 files, then on his next calls, there is no way
he could be upgraded, since he doesn't meet the needs of line 7).
To do this, you would need to append another set of rules
DIRECTLY to the end of the .CTL file.. You should have one
blank line between the sets of rules.. An example of a second set of
rules added to that first one, is:
SecLvlmin 1
SecLvlMax 10
TimesPosted 3
Times 2
Downloads -2
SecLvlNew 20
Seclvlmin 20
seclvlmax 30
timesposted -10
downloads 10
seclvlnew 5
Boardnumber 3
This second det of rules would take any user who is between level
20 and 30, and put them *DOWN* to level 10, if they had posted
less than 10 messages, and downloaded 10 or more files. As you
can see, the number of calls, or messages read would make no
impact in the second set of rules. Any user having his/her
access changed by the second set of rules in this example would
also recieve a message in base number 3, notifying them that they
have been automatically decreased by AutoUpdate due to their
participation level.
UPDATE terminates when one of three things happens:
1> End of the .CTL file is reached
2> 2 blank lines in a row are reached
3> Seclvlmax = 0 and seclvlnew = 0 in any particular set of
rules. in a set of rules with these parameters, no change
would be possible, so the program assumes you are done.
You can have as many sets of rules as you want. The system will
go through the entire userlog once for each rule, so the more
rules you have, the longer the run will take.
As the program runs, it will print "Checking users..." each time
it loads a new set of rules, just to let you know it is working.
It will also list each user who recieves a message.
As for where the program is to be run, you must be in the same
directory as the UPDATE.CTL, MSG*.BBS, and USERS.BBS files, but the
UPDATE.EXE can be anywhere in the path.
I am sorry the documentation isn't the best in the world, but, I
believe they are good enough to get the job done. If you have
any additions which would be good to make, in the program, or the
docs, please let me know, I will do my best, although working 2
jobs, and going to school part time prevents me from spending
much time on anything that isn't a change which is useful to
everyone.
I will do my best to reply to all NetMail, or mesages in the
QuickBBS echo, addressed to me, (Steve Jones or SysOp) at 109/410,
and also to mail recieved with a SASE through normal mail.
Well.. Have fun with all the time this program should save you
in manual updates of your userlog!
Thank you for using AutoUpdate 2.00. Please pass the
UPDATE20.ARC file on to other BBS's, and QuickBBS sysops and
potential SysOps.
Steve Jones, 109/410
Midi Thru BBS
(301)384-0351 2400 baud 24 hours, #CM